Class Viewer #29463

Closed
opened 2011-11-30 08:03:07 +01:00 by Alfonso de Leon Serra · 6 comments

Project: Blender Extensions
Tracker: Py Scripts Contrib
Blender: 2.60
Author(s): Mackraken
Script name: Class Viewer
Homepage: https://sites.google.com/site/aleonserra/home/scripts/class-viewer
Wiki page: https://sites.google.com/site/aleonserra/home/scripts/class-viewer
Category: Development
SVN Download: https://svn.blender.org/svnroot/bf-extensions/contrib/py/scripts/addons/development_class_viewer.py
Status: Open

%%%This script creates a contextual menu at the text editor window that helps you to quickly find a python class, a definition or a custom comment. When you select any item the cursor will jump to the line where that item is.

Use right click at the text editor to display the menu.%%%

**Project**: Blender Extensions **Tracker**: Py Scripts Contrib **Blender**: 2.60 **Author(s)**: Mackraken **Script name**: Class Viewer **Homepage**: https://sites.google.com/site/aleonserra/home/scripts/class-viewer **Wiki page**: https://sites.google.com/site/aleonserra/home/scripts/class-viewer **Category**: Development **SVN Download**: https://svn.blender.org/svnroot/bf-extensions/contrib/py/scripts/addons/development_class_viewer.py **Status**: Open %%%This script creates a contextual menu at the text editor window that helps you to quickly find a python class, a definition or a custom comment. When you select any item the cursor will jump to the line where that item is. Use right click at the text editor to display the menu.%%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'

This task was automatically closed as archived as part of migration, because it was determined to be no longer active.

The authoritative list of addons is on the wiki, we no longer have a report for each addon to track bugs and updates. Bugs can be reported individually and assigned to the addon developers. See the #Addons project page for more information on the workflow.

This task was automatically closed as archived as part of migration, because it was determined to be no longer active. The authoritative list of addons is on the wiki, we no longer have a report for each addon to track bugs and updates. Bugs can be reported individually and assigned to the addon developers. See the #Addons project page for more information on the workflow.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Member

%%%[canned response]

We gave you bf-extensions rights, read details at:


  • You can work on svn in contrib/ directory
See a help panel about svn here:
http://wiki.blender.org/index.php/Dev:Extensions/Sharing/SVN_Help
Don\'t forget to add a meaningful message at each svn commit
The password for svn is the same as the one you use to log in in this tracker.
  • We invited you to our commits mailing list
see http://lists.blender.org/mailman/listinfo/bf-extensions-cvs
Please subscribe, so that your commit mail will be sent to

subscribers instead of hanging on

You should have received a mail already about it, if not,

please leave a line here, thx!

  • Move your script in contrib/ directory in svn (if it's not
    there already)

  • We are assigning this script to yourself, so that you are
    responsible for maintenance.

Please click on "Monitor" to receive updates when people edit

your extension tracker page

  • Finally, we have moved this tracker page from the original
    location in "Upload", so check the tracker_url field and commit
    in bf-extensions

Thanks and welcome aboard! :)%%%

%%%[canned response] We gave you bf-extensions rights, read details at: - http://wiki.blender.org/index.php/Dev:Py/Sharing - http://wiki.blender.org/index.php/Dev:2.5/Py/Scripts/Guidelines/Addons ----- * You can work on svn in contrib/ directory ``` See a help panel about svn here: http://wiki.blender.org/index.php/Dev:Extensions/Sharing/SVN_Help ``` ``` Don\'t forget to add a meaningful message at each svn commit ``` ``` The password for svn is the same as the one you use to log in in this tracker. ``` * We invited you to our commits mailing list ``` see http://lists.blender.org/mailman/listinfo/bf-extensions-cvs ``` ``` Please subscribe, so that your commit mail will be sent to ``` subscribers instead of hanging on ``` You should have received a mail already about it, if not, ``` please leave a line here, thx! * Move your script in contrib/ directory in svn (if it\'s not there already) * We are assigning this script to yourself, so that you are responsible for maintenance. ``` Please click on "Monitor" to receive updates when people edit ``` your extension tracker page * Finally, we have moved this tracker page from the original location in "Upload", so check the tracker_url field and commit in bf-extensions Thanks and welcome aboard! :)%%%
Member

%%%Failed to byte-compile as:

py_compile.compile("development_class_viewer.py")

Sorry: TabError: inconsistent use of tabs and spaces in indentation (development_class_viewer.py, line 41)

Only line 40 is indented by space characters, while all other lines are indented by tab characters.

Please use only space characters for the indentation in all lines.

r2688
%%%

%%%Failed to byte-compile as: >>> py_compile.compile("development_class_viewer.py") Sorry: TabError: inconsistent use of tabs and spaces in indentation (development_class_viewer.py, line 41) >>> Only line 40 is indented by space characters, while all other lines are indented by tab characters. Please use only space characters for the indentation in all lines. r2688 %%%
Member

%%%Hi,
Due to changes to the api including the merging of bmesh, several addons are outdated.
Please, if you are the author of an addon check your script with blender revision 44256 or newer.
That is builds made After blender 2.62 official release.
I would ask that updates be made to your addon before the Blender 2.63 release.
6-8 weeks away.
This allows time for the api to become more exposed & bmesh to stablize furthur.
If you need help, drop into irc freenode #blenderpython or #blendercoders & feel welcome to ask questions.
At the time of 2.63 release, scripts that are not repaired or in active developement will have their tracker page marked "Closed"
this will not affect your links to the tracker, similar to closing scripts in 2.49b, the page will be still availible & can be re-opened.

Thanks for your understanding & patience during these Exciting Times.
Brendon.%%%

%%%Hi, Due to changes to the api including the merging of bmesh, several addons are outdated. Please, if you are the author of an addon check your script with blender revision 44256 or newer. That is builds made After blender 2.62 official release. I would ask that updates be made to your addon before the Blender 2.63 release. 6-8 weeks away. This allows time for the api to become more exposed & bmesh to stablize furthur. If you need help, drop into irc freenode #blenderpython or #blendercoders & feel welcome to ask questions. At the time of 2.63 release, scripts that are not repaired or in active developement will have their tracker page marked "Closed" this will not affect your links to the tracker, similar to closing scripts in 2.49b, the page will be still availible & can be re-opened. Thanks for your understanding & patience during these Exciting Times. Brendon.%%%
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#29463
No description provided.